Do one of the following solutions:
Solution 1: Rename the Adobe Premiere Pro executable file.
Rename Adobe Premiere Pro.exe.
Note: Under certain circumstances, Premiere Pro 1.0 may become unstable if you rename Adobe Premiere Pro.exe. There are no issues known to occur if you rename Adobe Premiere Pro.exe with Premiere Pro 1.5.
To rename Adobe Premiere Pro.exe:
1. Locate Adobe Premiere Pro.exe. The default location is Program Files\Adobe\Premiere Pro 1.x.
Note : By default, Windows doesn't display filename extensions it recognizes. If the .EXE file extension isn't visible, configure Windows to display all file extensions. See "Display hidden files and folders" in Windows Help for instructions.
2. Right-click Adobe Premiere Pro.exe and choose Rename.
3. Rename Adobe Premiere Pro.exe to Premiere Pro.exe.
Solution 2: Change the affinity setting for the Adobe Premiere Pro.exe process to use only one CPU.
1. Start Adobe Premiere Pro.
2. Press Ctrl + Alt + Delete and then click Task Manager.
3. Click the Processes tab.
4. Right-click the process Adobe Premiere Pro.exe, and then choose Set Affinity.
5. Deselect all CPUs except the first CPU listing (CPU 0) and then click OK.
6. Quit the Task Manager.
Note : The affinity setting only remains active until you quit Adobe Premiere Pro, at which time it returns to the default setting.
Solution 3: Disable hyperthreading in the system BIOS.
Refer to the computer or motherboard documentation for information on entering and modifying the system BIOS.
Background Information
Microsoft Windows XP Service Pack 2 includes updates designed to improve window and menu handling in Premiere Pro 1.0. This special code is no longer required for Premiere Pro 1.5, and may cause issues with the Adobe Media Encoder. Renaming Adobe Premiere Pro.exe prevents the code from activating.
Bookmarks